Ceasing transmission repetitions

ABSTRACT

Apparatuses, methods, and systems are disclosed for ceasing transmission repetition. One apparatus includes a transmitter that transmits data to a base unit in a first transmission time interval (“TTI”). Here, the data is configured for transmission with a predetermined number of repetitions. The apparatus includes a receiver that receives a control signal from the base unit in a second TTI. The apparatus includes a processor that determines whether the control signal corresponds to the data and, in response to the control signal corresponding to the data, determines whether to cease at least one transmission repetition of the data before the number of repetitions reaches the predetermined number.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to early termination ofuplink transmission repetition.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description.

Third Generation Partnership Project (“3GPP”), Positive-Acknowledgment(“ACK”), Access and Mobility Management Function (“AMF”), Binary PhaseShift Keying (“BPSK”), Carrier Aggregation (“CA”), Clear ChannelAssessment (“CCA”), Control Channel Element (“CCE”), Cyclic Prefix(“CP”), Channel State Information (“CSI”), Common Search Space (“CSS”),Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information(“DCI”), Downlink (“DL”), Downlink Pilot Time Slot (“DwPTS”), EnhancedClear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), European Telecommunications Standards Institute(“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex(“FDD”), Frequency Division Multiple Access (“FDMA”), Guard Period(“GP”), Hybrid Automatic Repeat Request (“HARQ”), Internet-of-Things(“IoT”), Key Performance Indicators (“KPI”), Licensed Assisted Access(“LAA”), Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), LongTerm Evolution (“LTE”), LTA Advanced (“LTE-A”), Medium Access Control(“MAC”), Multiple Access (“MA”), Modulation Coding Scheme (“MCS”),Machine Type Communication (“MTC”), Massive MTC (“mMTC”), Multiple InputMultiple Output (“MIMO”), Multi User Shared Access (“MUSA”), Narrowband(“NB”), Negative-Acknowledgment (“NACK”) or (“NAK”), New Data Indicator(“NDI”), Network Function (“NF”), Next Generation Node B (“gNB”),Non-Orthogonal Multiple Access (“NOMA”), Orthogonal Frequency DivisionMultiplexing (“OFDM”), Primary Cell (“PCell”), Physical BroadcastChannel (“PBCH”), Physical Downlink Control Channel (“PDCCH”), PhysicalDownlink Shared Channel (“PDSCH”), Pattern Division Multiple Access(“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”), PhysicalRandom Access Channel (“PRACH”), Physical Resource Block (“PRB”),Physical Uplink Control Channel (“PUCCH”), Physical Uplink SharedChannel (“PUSCH”), Quality of Service (“QoS”), Quadrature Phase ShiftKeying (“QPSK”), Radio Resource Control (“RRC”), Random Access Procedure(“RACH”), Random Access Response (“RAR”), Reference Signal (“RS”),Resource Spread Multiple Access (“RSMA”), Round Trip Time (“RTT”),Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request(“SR”), Session Management Function (“SMF”), Sounding Reference Signal(“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”),Secondary Cell (“SCell”), Shared Channel (“SCH”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Transmission and Reception Point (“TRP”), Transmission Time Interval(“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), UserEntity/Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), User PlaneFunction (“UPF”), Universal Mobile Telecommunications System (“UMTS”),Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NAK”).ACK means that a TB is correctly received while NAK means a TB iserroneously received.

In 5G networks, URLLC UL traffic may be sent using grant-free based ULtransmission configured for a predetermined number of transmissionrepetitions. Transmission repetitions of the UL traffic is unnecessaryonce the gNB successfully receives the UL traffic, and the UE continuingthe predetermined number of transmission repetitions wastes resources ifthe gNB has successfully received the UL traffic. However, there is nomechanism for the UE to stop the transmission repetitions when the gNBsuccessfully receives the UL traffic.

BRIEF SUMMARY

Methods for early termination of uplink transmission repetition aredisclosed. Apparatuses and systems also perform the functions of themethods. The methods may also be embodied in one or more computerprogram products comprising executable code.

In one embodiment, a method for early termination of uplink transmissionrepetition includes transmitting data to a base unit in a first TTI.Here, the data is configured for transmission with a predeterminednumber of repetitions. The method also includes receiving a controlsignal from the base unit in a second TTI and determining whether thecontrol signal corresponds to the data. In response to the controlsignal corresponding to the data, the method includes determiningwhether to cease at least one transmission repetition of the data beforethe number of repetitions reaches the predetermined number.

Another method for early termination of uplink transmission repetitionincludes receiving a data from a remote unit in a first TTI. Here, thedata is configured for transmission with a predetermined number ofrepetitions. The method includes determining whether the data issuccessfully received and transmitting a control signal to the remoteunit in a second TTI. Here, the control signal corresponds to the dataand includes an indicator for indicating whether the data issuccessfully received.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for early termination of uplinktransmission repetition;

FIG. 2 illustrates one embodiment of a network architecture for earlytermination of uplink transmission repetition;

FIG. 3 is a schematic block diagram illustrating one embodiment of acomputing device for early termination of uplink transmissionrepetition;

FIG. 4 is a schematic block diagram illustrating another embodiment of acomputing device for early termination of uplink transmissionrepetition;

FIG. 5 is a block diagram illustrating one embodiment of earlytermination of uplink transmission repetition using an included TTIoffset to indicate correspondence between a DL control signal andpreviously received UL data;

FIG. 6 is a block diagram illustrating one embodiment of earlytermination of uplink transmission repetition using an included TTIindex to indicate correspondence between a DL control signal andpreviously received UL data;

FIG. 7 is a block diagram illustrating one embodiment of earlytermination of uplink transmission repetition using a preconfigured TTIoffset to indicate correspondence between a DL control signal andpreviously received UL data;

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method for early termination of uplink transmission repetition

FIG. 9 is a schematic flow chart diagram illustrating another embodimentof a method for early termination of uplink transmission repetition.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special-purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theschematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

In order to solve the above described problem of unnecessary ULtransmission repetitions after successful reception of the UL data, thegNB or the base unit sends an indicator (e.g., an ACK bit) to the UE anda control signal, such as a UL grant. However, the UE needs to determinewhether the UL grant corresponds to the UL data. Accordingly, the gNBuses a TTI offset and/or TTI index to indicate correspondence betweenthe control signal (e.g., UL grant) and the UL data. After determiningthat the control signal corresponds to the previously transmitted ULdata, the UE examines the indicator contained in control signal andstops transmission repetition before reaching the predetermined numberof repetitions in response to the indicator indicating that the data wassuccessfully received.

FIG. 1 depicts a wireless communication system 100 for early terminationof uplink transmission repetition, according to embodiments of thedisclosure. In one embodiment, the wireless communication system 100includes remote units 105, base units 110, and communication links 115.Even though a specific number of remote units 105, base units 110, andcommunication links 115 are depicted in FIG. 1, one of skill in the artwill recognize that any number of remote units 105, base units 110, andcommunication links 115 may be included in the wireless communicationsystem 100.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTE-Aor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, user equipment (“UE”),user terminals, a device, or by other terminology used in the art. Theremote units 105 may communicate directly with one or more of the baseunits 110 via uplink (“UL”) and downlink (“DL”) communication signals,for example a remote unit 105 may send data in a transmission block(“TB”) to a base unit 110 via UL communication signals and receive dataor control signals from the base unit via DL communication signals.Furthermore, the UL and DL communication signals may be carried over thecommunication links 115.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, an access point, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, or by any other terminologyused in the art. The base units 110 are generally part of a radio accessnetwork (“RAN”) that may include one or more controllers communicablycoupled to one or more corresponding base units 110. The RAN isgenerally communicably coupled to one or more core networks, which inturn may be coupled to other networks, like the Internet and publicswitched telephone networks, among other networks. These and otherelements of radio access and core networks are not illustrated but arewell known generally by those having ordinary skill in the art. The baseunits 110 connect to the mobile core network 130 via the RAN.

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 110 may communicate directly with oneor more of the remote units 105 via communication signals. Generally,the base units 110 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe communication links 115. The communication links 115 may be anysuitable carrier in licensed or unlicensed radio spectrum. Thecommunication links 115 facilitate communication between one or more ofthe remote units 105 and/or one or more of the base units 110.

In one embodiment, the mobile core network 130 is a 5G core (“5GC”) orthe evolved packet core (“EPC”), which may be coupled to other datanetwork 125, like the Internet and private data networks, among otherdata networks. Each mobile core network 130 belongs to a single publicland mobile network (“PLMN”). The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The mobile core network 130 includes several network functions (“NFs”).As depicted, the mobile core network 130 includes an access and mobilitymanagement function (“AMF”) 135, a session management function (“SMF”)140, and a user plane function (“UPF”) 145. Although a specific numberof AMFs 135, SMFs 140, and UPFs 145 are depicted in FIG. 1, one of skillin the art will recognize that any number of AMFs 135, SMFs 140, andUPFs 145 may be included in the mobile core network 130.

The AMF 135 provides services such as UE registration, UE connectionmanagement, and UE mobility management. The SMF 140 manages the datasessions of the remote units 105, such as a PDU session. The UPF 145provides user plane (e.g., data) services to the remote units 105. Adata connection between the remote unit 105 and a data network 125 ismanaged by a UPF 145.

As discussed in further detail below, a remote unit 105 may beconfigured to repeat UL transmissions a predetermined number of times toensure their reception at the base unit 110. However, the remote unit105 unnecessarily uses radio resources repeating the UL transmissionsonce the base unit 110 has successfully received the data. As usedherein, the base unit 110 “successfully receives” the data by receivingthe uplink signal containing the uplink data at its receiver andsuccessfully decoding the uplink data from the uplink signal.Accordingly, the base unit 110 may indicate that it has successfullyreceived the uplink data, wherein the remote unit 105 ceases anyremaining transmission repetitions of the uplink data in response toreceiving an indication of success.

FIG. 2 depicts a network 200 used for early termination of uplinktransmission repetition, according to embodiments of the disclosure. Thenetwork 200 includes a UE 205 and gNB 210. The network 200 depicts asimplified embodiment of the wireless communication system 100. The UE205 may be one embodiment of the remote unit 105, while the gNB 210 maybe one embodiment of the base unit 110. Here, the gNB 210 may be a gNBor 5G base station. Although only one UE 205 is depicted, in otherembodiments the gNB 210 may serve a plurality of UEs 205.

As depicted, the UE 205 transmits data, here the UL TB 215, and a firstTTI over an UL channel, such as a PUSCH. The TTI may be a slot, a minislot, or the like. The UL TB 215 may be for a URLLC service requiringshorter latency tolerance and higher transmission reliability than aneMBB service. As such, the UL TB 215 may be sent using grant-free ULtransmission to satisfy the latency requirement. Further, in order tosatisfy the reliability requirement, the UL TB 215 may be repeated K atotal of times (to include the initial transmission), where K is apredetermined number greater than or equal to one.

However, it is inefficient for the UE 205 to continue transmissionrepetitions of the UL TB 215 once the gNB 210 successfully receives theUL TB 215. The gNB 210 responds to the UL TB 215 with a (DL) controlsignal 220, such as a DCI and/or a UL grant. Note that the gNB 210 sendsthe control signal 220 in a second, subsequent TTI. For more efficientresource use, the gNB 210 indicates to UE 205 that the control signal220 corresponds to the received UL TB 215 and indicates whether the ULTB 215 was successfully received. The UE 205 determines whether thecontrol signal 220 corresponds to the UL TB 215 and ceases any remainingtransmission repetitions of the UL TB 215 upon the gNB 210 indicatingthat the UL TB 215 was successfully received. As used herein, the gNB210 “successfully receives” the data by receiving the uplink signalcontaining the uplink data at its receiver and successfully decoding theuplink data from the uplink signal.

To facilitate early termination of UL transmission repetitions (e.g., inresponse to successful reception of the uplink data), the UE 205 needsto determine whether a received control signal 220 (e.g., UL grant) isfor the UL TB 215. In one embodiment, the UE 205 attempts to discoverwhether a UL grant corresponds to the UL TB 215 immediately after itbegins transmitting the UL TB 215 on the PUSCH in grant-free mode. Inanother embodiment, the UE 205 waits a predetermined amount of timeafter transmitting the UL TB 215 on the PUSCH before attempting todiscover whether the UL grant corresponds to the UL TB 215.

If the control signal 220 corresponds to the UL TB 215, then the UE 205continues to determine whether the control signal 220 is for schedulinga retransmission of the UL TB 215 (e.g., using grant-based transmission)or an indication to stop transmission repetition of the UL TB 215.Otherwise, if the control signal 220 is not corresponds to the UL TB215, then the UE 205 transmits new data on the PUSCH according to areceived UL grant. To prevent confusion, the UE 205 only sends one PUSCHin one TTI. Further, at the UE 205 a UL grant triggered PUSCH overridesany grant-free PUSCH in a given TTI.

In some embodiments, the gNB 210 uses a bit field in the control signal220 to implicitly indicate whether the control signal 220 corresponds tothe UL TB 215. For example, a TTI offset and/or a TTI index of thecontrol signal 220 may be used to implicitly indicate that the controlsignal 220 corresponds to the UL TB 215. To prevent confusion, the UE205 and the gNB 210 maintain the same understanding on the meaning of aTTI offset. FIGS. 5-7 depict various embodiments of using the TTI offsetand/or TTI index of the control signal 220 to implicitly indicate thecorrespondence.

After determining that the control signal 220 corresponds to the UL TB215, the UE 205 examines the control signal 220 to determine whether theUL TB 215 was successfully received at the gNB 210. In some embodiments,the UE 205 reinterprets an NDI field in the control signal 220 as anACK/NAK value. In contrast to conventional usage, then the NDI fieldhere indicates whether the UL TB 215 was successfully received (e.g.,using an ACK bit value) or was unsuccessfully received (e.g., using aNAK bit value). To prevent confusion, the UE 205 and the gNB 210maintain the same understanding on the meaning of the NDI field. In oneembodiment, the meaning of the NDI field, when the control signal 220 issent in response to the UL TB 215, is predefined in a communicationstandard specification used by both the UE 205 and the gNB 210. Incertain embodiments, the meaning of the NDI field, when reinterpreted asan ACK/NAK indication, is fixed. In other embodiments, the meaning ofthe NDI field may be preconfigured for the UE 205.

FIG. 3 depicts one embodiment of a remote apparatus 300 that may be usedfor early termination of uplink transmission repetition, according toembodiments of the disclosure. The remote apparatus 300 may be oneembodiment of the remote unit 105 and/or UE 205, described above.Furthermore, the remote apparatus 300 may include a processor 305, amemory 310, an input device 315, an output device 320, a transceiver 325for communicating with one or more base units 110.

As depicted, the transceiver 325 may include a transmitter 330 and areceiver 335. The transceiver 325 may also support one or more networkinterfaces 340, such as the Uu interface used to communicate with a gNB.In some embodiments, the input device 315 and the output device 320 arecombined into a single device, such as a touchscreen. In certainembodiments, the remote apparatus 300 may not include any input device315 and/or output device 320.

The processor 305, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 305 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 305 executes instructions stored in thememory 310 to perform the methods and routines described herein. Theprocessor 305 is communicatively coupled to the memory 310, the inputdevice 315, the output device 320, and the transceiver 325.

In some embodiments, the transmitter 330 transmits data (e.g., a UL TB)to a base unit 110 in a first TTI. The TTI may be a slot, a mini-slot,or other defined time interval. Here, the data is configured fortransmission with a predetermined number of repetitions. For example,the transmitter 330 may be configured to send a total of 10 repetitionsof the UL TB, each in a different TTI. In certain embodiments, thetransmitter 330 transmits the data using a grant-free mechanism. Inother embodiments, the transmitter 330 transmits the data on ULresources indicated in an UL grant. In one embodiment, the data sent inthe first TTI is an initial transmission of the data. In anotherembodiment, the data sent in the first TTI is a retransmission of thedata (e.g., a subsequent transmission repetition).

The receiver 335 receives a control signal (e.g., a DCI and/or UL grant)from the base unit 110 in a second TTI. Here, the second TTI occursafter the first TTI. In one embodiment, the second TTI is at least aminimum number of TTIs after the first TTI. In certain embodiments, thesecond TTI has the same duration as the first TTI.

In response to the receiver 335 receiving the control signal, theprocessor 305 determines whether the control signal corresponds to thedata (e.g., is a response to the UL TB). If the control signalcorresponds to the data, then the processor 305 determines whether tocease any remaining transmission repetitions of the data before thenumber of repetitions reaches the predetermined number (e.g., earlytermination of the UL transmission repetitions).

In some embodiments, the processor 305 determines whether the controlsignal corresponds to the data by identifying a TTI offset, calculatinga TTI (e.g., a target TTI) from the second TTI and the identified TTIoffset, and determining whether the calculated TTI matches to the firstTTI. Here, the control signal corresponds to the data if the calculatedTTI matching the first TTI.

In certain embodiments, the processor 305 identifies the TTI offset froma bit field contained in the control signal. In one embodiment, thevalue in the bit field corresponds to the amount of TTI offset. Inanother embodiment, the value in the bit field indicates a TTI offsetfrom a set of TTI offsets. Here, the set of TTI offsets may bepreconfigured by the base unit or predefined in a communication standardspecification used by the remote apparatus 300 and the base unit 110,for example prior to the transmitter 330 sending the UL TB. In otherembodiments, the TTI offset may be a fixed value (e.g., predefined in atelecommunications standard used by the remote apparatus 300) orsemi-statically configured by the base unit 110. Here, the TTI offset ispreconfigured by the base unit prior to the transmitter 330 transmittingthe data.

In some embodiments, the processor 305 determines whether the controlsignal corresponds to the data by identifying a TTI index contained inthe control signal. The processor 305 then determines whether theidentified TTI index matches to the first TTI. Here, the control signalcorresponds to the data in response to the identified TTI index matchingthe first TTI.

In certain embodiments, the transmitter 330 sends a transmissionrepetition of the UL TB in a third TTI prior to the receiver 335receiving the control signal. Here, the processor 305 determines whetherthe control signal corresponds to the UL TB by determining whether theTTI offset points to the third TTI or whether the TTI index matches thethird TTI.

Where the control signal corresponds to the UL data, the control signalincludes an indicator for indicating whether the data is successfullyreceived. In some embodiments, the processor 305 determines whether tocease any remaining transmission repetitions of the data before thenumber of repetitions reaches the predetermined number by interpretingthe indicator to determine whether the data is successfully received. Incertain embodiments, the indicator replaces the NDI field in the controlsignal. In such embodiments, the processor 305 reinterprets the NDIfield as an ACK/NAK bit, such that the reinterpreted NDI indicateswhether the data is successfully received. For example, a bit value of“1” may be an ACK indicating successful reception of the data, while abit value of “0” may be a NAK indicating unsuccessful reception of thedata.

In response to the indicator indicating that the data is successfullyreceived, the transmitter 330 ceases at least one transmissionrepetition (e.g., all remaining transmission repetitions) of the databefore the number of repetitions reaches the predetermined number. Inone embodiment, the transmitter 330 continues repeating the data untilthe number of repetitions reaches the predetermined number in responseto the indicator indicating that the data is not successfully received.In another embodiment, the transmitter 330 transmits the data based onscheduling of the control signal in response to the indicator indicatingthat the data is not successfully received.

The memory 310, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 310 includes volatile computerstorage media. For example, the memory 310 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 310 includes non-volatilecomputer storage media. For example, the memory 310 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 310 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 310 stores data relating to earlytermination of uplink transmission repetition. For example, the memory310 may store TTI values, TTI offsets, and the like. In someembodiments, the memory 310 also stores program code and related data,such as an operating system or other controller algorithms operating onthe remote unit 105 and one or more software applications.

The input device 315, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 315 maybe integrated with the output device 320, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 315 includes two or more different devices, such as a keyboardand a touch panel. In certain embodiments, the input device 315 mayinclude a camera for capturing images or otherwise inputting visualdata.

The output device 320, in one embodiment, may include any knownelectronically controllable display or display device. The output device320 may be designed to output visual, audible, and/or haptic signals. Insome embodiments, the output device 320 includes an electronic displaycapable of outputting visual data to a user. For example, the outputdevice 320 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user.

In certain embodiments, the output device 320 includes one or morespeakers for producing sound. For example, the output device 320 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 320 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 320 may beintegrated with the input device 315. For example, the input device 315and output device 320 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 320 may be located nearthe input device 315.

The transceiver 325 communicates with base units 110 of a mobilecommunication network. The transceiver 325 may include one or moretransmitters 330 and one or more receivers 335. As discussed above, thetransceiver 325 may support one or more the network interface 340 forcommunicating with the base unit 110.

FIG. 4 depicts one embodiment of a base station apparatus 400 that maybe used for early termination of uplink transmission repetition,according to embodiments of the disclosure. The base station apparatus400 may be one embodiment of the base unit 110 and/or gNB 210, describedabove. Furthermore, the base station apparatus 400 may include aprocessor 405, a memory 410, an input device 415, an output device 420,a transceiver 425 for communicating with one or more remote units 105and/or a mobile core network 130.

As depicted, the transceiver 425 may include a transmitter 430 and areceiver 435. The transceiver 425 may also support one or more networkinterfaces 440, such as the Uu interface, N2 interface, N3 interface,and/or other network interfaces suitable for communication with a remoteunit and/or core network. In some embodiments, the input device 415 andthe output device 420 are combined into a single device, such as atouchscreen. In certain embodiments, the base station apparatus 400 maynot include any input device 415 and/or output device 420.

The processor 405, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 405 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 405 executes instructions stored in thememory 410 to perform the methods and routines described herein. Theprocessor 405 is communicatively coupled to the memory 410, the inputdevice 415, the output device 420, and the transceiver 425.

In some embodiments, the receiver 435 receives data (e.g., a UL TB) froma remote unit 105, the data being sent in a first transmission timeinterval (“TTI”). In certain embodiments, the data is configured fortransmission with a predetermined number of repetitions. The processor405 determines whether the data is successfully received. Thetransmitter 430 transmits a control signal to the remote unit in asecond TTI. Here, the control signal corresponds to the received dataand includes an indicator for indicating whether the data issuccessfully received.

In certain embodiments, the processor 405 uses a TTI offset between thefirst TTI and the second TTI to indicate association between the controlsignal and the data. For example, the processor 405 may include a bitfield in the control signal to indicate the TTI offset. In oneembodiment, the bit field included in the control signal may indicate aTTI offset from a set of TTI offsets. Here, the set of TTI offsets maybe preconfigured for the remote unit 105 or predefined in acommunication standard specification used by the base station apparatus400 and the remote unit 105. In other embodiments, the TTI offsetbetween the first TTI and the second TTI is a fixed value or ispreconfigured for the remote unit 105 before the remote unit 105transmits the data. In certain embodiments, the processor 405 uses a TTIindex of the first TTI to designate association between the controlsignal and the data. For example, the processor 405 may include a bitfield in the control signal that specifies the TTI index of the firstTTI to designate the association.

In some embodiments, the processor 405 indicates whether the data issuccessfully received by setting the value of an NDI field to an ACK orNAK value, based on whether the data (UL TB) was successfully received.This is in contrast to conventional NDI usage where a change in thevalue (e.g., the value toggling from a “0” to a “1”, or vice versa) isused to indicate that new data is to be sent. Thus, the indicator may berealized by the remote unit 105 reinterpreting the NDI in the controlsignal. In other embodiments, the indicator for indicating whether thedata is successfully received replaces the NDI in the control signal. Incertain embodiments, the indicator is one bit in the control signal(e.g., an ACK/NAK bit) whose value indicates whether the data issuccessfully received. When the indicator indicates that the data issuccessfully received, then the remote unit 105 ceases transmissionrepetition of the data (e.g., UL TB) before the number of repetitionsreaches the predetermined number. Otherwise, the remote unit 105continues transmission repetition of the data until wither thepredetermined number of repetitions occur or a new (e.g., subsequent)indicator in a later received control signal indicates that the data issuccessfully received.

The memory 410, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 410 includes volatile computerstorage media. For example, the memory 410 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 410 includes non-volatilecomputer storage media. For example, the memory 410 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 410 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 410 stores data relating to earlytermination of uplink transmission repetition. For example, the memory410 may store TTI values, TTI offsets, and the like. In someembodiments, the memory 410 also stores program code and related data,such as an operating system or other controller algorithms operating onthe remote unit 105 and one or more software applications.

The input device 415, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 415 maybe integrated with the output device 420, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 415 includes two or more different devices, such as a keyboardand a touch panel. In certain embodiments, the input device 415 mayinclude a camera for capturing images or otherwise inputting visualdata.

The output device 420, in one embodiment, may include any knownelectronically controllable display or display device. The output device420 may be designed to output visual, audible, and/or haptic signals. Insome embodiments, the output device 420 includes an electronic displaycapable of outputting visual data to a user. For example, the outputdevice 420 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user.

In certain embodiments, the output device 420 includes one or morespeakers for producing sound. For example, the output device 420 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 420 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 420 may beintegrated with the input device 415. For example, the input device 415and output device 420 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 420 may be located nearthe input device 415.

The transceiver 425 communicates with remote unit within a mobilecommunication network. The transceiver 425 may also communicate with acore network, such as the mobile core network 130. The transceiver 425may include one or more transmitters 430 and one or more receivers 435.As discussed above, the transceiver 425 may supports one or more thenetwork interface 440 for communicating with remote units 105 and themobile core network 130.

FIG. 5 depicts a procedure 500 for early termination of uplinktransmission repetition by using an included TTI offset to indicatecorrespondence between a DL control signal and previously received ULdata (e.g., the UL TB 215). The procedure 500 involves communicationbetween the UE 205 and the gNB 210. The UE 205 may be one embodiment ofthe remote unit 105 and/or the remote apparatus 300, discussed above.The gNB 210 may be one embodiment of the base unit 110 and/or the basestation apparatus 400, discussed above.

As depicted, the procedure 500 begins and the UE 205 generates uplinkdata to be transmitted to the gNB 210 (see item 505). Accordingly, theUE 205 sends an uplink data transmission (item 510) to the gNB 210, theuplink data transmission including uplink data 511. Here, the uplinkdata 511 may be one embodiment of the UL TB 215 discussed above. In someembodiments, the UE 205 sends the uplink data transmission usinggrant-free UL transmission resources. For example, the gNB 210 maypreconfigure a transmission resource pool for grant-free UL transmissionfor URLLC service.

The UE 205 is configured to send K repetitions of the uplink data 511,where K is a predetermined value (e.g., previously configured by the gNB210). Here the K repetitions includes the initial uplink datatransmission (item 510) and one or more subsequent transmissionrepetitions (item 515). Each subsequent transmission repetition includesa copy of the uplink data 511. Here, the initial transmission is sent ona first TTI, while the one or more subsequent transmission repetitionsare send on subsequent TTIs.

After receiving the initial uplink data transmission (or a subsequenttransmission repetition), the gNB 210 determines whether the uplink data511 is successfully received. The uplink data 511 is successfullyreceived when the gNB 210 is able to decode it. Similarly, the uplinkdata 511 is not successfully received when the gNB 210 is unable todecode it. Next, the gNB 210 generates a control signal 520, such as aDCI and/or UL grant, for transmission to the UE 205. As depicted, thecontrol signal 520 includes a TTI offset field 525 and an indicator 530.The indicator 530 indicates whether the uplink data 511 is successfullyreceived at the gNB 210.

The TTI offset is a dynamic indication of a TTI to which the controlsignal 520 corresponds (e.g., the TTI of the initial uplink datatransmission or a subsequent transmission repetition). To indicate thatthe control signal 520 corresponds to the initial uplink datatransmission, the gNB 210 sets the bits in the TTI offset field 525 to avalue that points to the TTI of the initial uplink data transmission.For example, if the initial uplink data transmission is sent during afirst TTI having a value of “Z” and the control signal to 220 istransmitted during a second TTI having a value of “Y”, then the gNB 210calculates a TTI offset of “X” such that “Y”−“X”=“Z”. To indicate thatthe control signal 520 corresponds to a subsequent transmissionrepetition, the gNB 210 sets the bits in the TTI offset field 525 to avalue that points to the TTI of the subsequent transmission repetition.

The TTI offset between the UE 205 transmitting the grant-free PUSCH(e.g., the initial uplink data transmission at 510 or a subsequenttransmission repetition at 515) and the gNB 210 transmitting the controlsignal 520 is dependent on processing capabilities of the UE 205 and gNB210 as well as latency requirements of the URLLC service. For example,if the gNB 210 fails to decode the uplink data 511, the gNB need toschedule an uplink resource for the UE 205 to retransmit the uplink data511 as soon as possible. Further, if the uplink data 511 is successfullydecoded at the gNB, then the gNB 210 to send an acknowledgment (e.g., anACK) to the UE 205 for the UE 205 to stop transmission repetition of theuplink data 511 before the number of repetitions (e.g., number of totaltransmissions of the uplink data 511) reaches K. In some embodiments,the TTI offset field 525 is a two bit value covering up to 4 TTIs ofoffset. In other embodiments, the TTI offset field 525 indicates aparticular TTI offset from a set of TTI offsets. Here, the set of TTIoffsets may be preconfigured by the gNB 210 or predefined in acommunication standard specification used by the UE 205 and gNB 210.

Upon receiving control signal 520, the UE 205 identifies the TTI offsetfield 525 (e.g., having the value “X”) and identifies the TTI (e.g., ofvalue “Y”) of the control signal 520. The UE 205 then calculates atarget TTI of “Y”−“X” and determines whether the target TTI matches thefirst TTI of the initial uplink data transmission (e.g., “Z”) or the TTIof a subsequent transmission repetition. Where the target TTI matchesthe TTI of a transmission of the uplink data 511, then the UE 205determines that the control signal 520 corresponds to the initial uplinkdata transmission. Otherwise, if the target TTI does not match the TTIof the initial uplink data transmission at 510 or a subsequenttransmission repetition at 515, then the UE 205 determines the controlsignal 520 does not correspond to the uplink data 511 and interprets thecontrol signal 520 conventionally.

In the depicted embodiment, the control signal 520 corresponds to theinitial uplink data transmission (item 510) and the UE 205 examines theindicator 530 to determine whether the uplink data 511 was successfullyreceived by the gNB 210. In certain embodiments, the indicator 530replaces the NDI field in an UL grant. Typically, the NDI field containsone bit indicating whether the UL grant is for new data or is to be usedfor UL transmission repetition. However, when the indicator 530 replacesthe NDI field, the corresponding bit is interpreted as ACK/NAK bit. Inone embodiment, a bit value of “1” in the NDI field indicates the uplinkdata 511 was successfully received (“ACK”) while a bit value of “0” inthe NDI field indicates that the uplink data 511 was unsuccessfullyreceived (“NAK”). In the case of ACK, the UE 205 terminates transmissionrepetition of uplink data 511. However, in the case of NAK, the UE 205retransmits the uplink data 511. In one embodiment, the UE 205retransmits the uplink data 511 using grant-free transmissionrepetition. Here, the UE 205 continues transmission repetition 515 ofthe uplink data 511 until either receiving subsequent indication ofsuccessful reception or until the number of repetitions reaches K. Inother embodiments, the UE 205 retransmits the uplink data 511 usinggrant-based transmission 535, for example using UL resources scheduledin the control signal 520.

FIG. 6 depicts a procedure 600 for early termination of uplinktransmission repetition by using an included TTI index to indicatecorrespondence between a DL control signal and previously received ULdata (e.g., the UL TB 215). The procedure 600 involves communicationbetween the UE 205 and the gNB 210. The UE 205 may be one embodiment ofthe remote unit 105 and/or the remote apparatus 300, discussed above.The gNB 210 may be one embodiment of the base unit 110 and/or the basestation apparatus 400, discussed above.

As depicted, the procedure 600 begins and the UE 205 generates uplinkdata to be transmitted to the gNB 210 (see item 605). Accordingly, theUE 205 sends an uplink data transmission (item 610) to the gNB 210, theuplink data transmission including uplink data 611. Here, the uplinkdata 611 may be one embodiment of the UL TB 215 discussed above. In someembodiments, the UE 205 sends the uplink data transmission usinggrant-free UL transmission resources. For example, the gNB 210 maypreconfigure a transmission resource pool for grant-free UL transmissionfor URLLC service.

The UE 205 is configured to send K repetitions of the uplink data 611,where K is a predetermined value (e.g., previously configured by the gNB210). Here the K repetitions of the uplink data 611 includes the initialuplink data transmission (item 610) and one or more subsequenttransmission repetitions (item 615). Each subsequent transmissionrepetition includes a copy of the uplink data 611. Here, the initialtransmission is sent on a first TTI, while the one or more subsequenttransmission repetitions are send on subsequent TTIs.

After receiving the initial uplink data transmission (or a subsequenttransmission repetition), the gNB 210 determines whether the uplink data611 is successfully received. The uplink data 611 is successfullyreceived when the gNB 210 is able to decode it. Similarly, the uplinkdata 611 is not successfully received when the gNB 210 is unable todecode it. Next, the gNB 210 generates a control signal 620, such as aDCI and/or UL grant, for transmission to the UE 205. As depicted, thecontrol signal 620 includes a TTI index field 625 and an indicator 630.The indicator 630 indicates whether the uplink data 611 is successfullyreceived at the gNB 210.

The TTI index field 625 explicitly indicates a TTI to which the controlsignal 620 corresponds (e.g., the TTI of the initial uplink datatransmission or a subsequent transmission repetition). To indicate thatthe control signal 620 corresponds to the initial uplink datatransmission, the gNB 210 sets the bits in the TTI index field 625 tomatch the TTI of the initial uplink data transmission. For example, ifthe initial uplink data transmission is sent during a first TTI having avalue of “Z”, then the gNB 210 sets the TTI index field 625 to also havethe value “Z”. This indicates that the control signal 620 corresponds toa PUSCH transmitted during the first TTI. To indicate that the controlsignal 620 corresponds to a subsequent transmission repetition, the gNB210 sets the bits in the TTI index field 625 to a value that matcheswith the TTI of the subsequent transmission repetition.

The interval between the UE 205 transmitting the grant-free PUSCH (e.g.,the initial uplink data transmission at 610 or a subsequent transmissionrepetition at 615) and the gNB 210 transmitting the control signal 620is dependent on processing capabilities of the UE 205 and gNB 210 aswell as latency requirements of the URLLC service. Generally, the gNB210 responds to the uplink data transmission with the control signal 620as soon as possible. If the uplink data 611 is successfully decoded atthe gNB, then the gNB 210 to send an acknowledgment (e.g., an ACK) tothe UE 205 for the UE 205 to stop transmission repetition of the uplinkdata 611 before the number of repetitions (e.g., number of totaltransmissions of the uplink data 611) reaches K.

The number of bits needed for the TTI index field 625 is dependent onthe number of TTI's within a radio frame. For example, a radio framethat includes 20 TTIs would require a TTI index field 625 with thelength of five bits. Here, the length of the TTI index field 625 may bepredefined in the communication standard specification or preconfiguredby the gNB 210. As compared to the TTI offset field 525, the TTI indexfield 625 may require more bits to indicate correspondence to particularUL transmission.

Upon receiving control signal 620, the UE 205 identifies the TTI indexfield 625 (e.g., having the value “Z”) and determines whether the TTI ofthe initial uplink data transmission (or the TTI of a subsequenttransmission repetition) matches the value in the TTI index field 625.Where the TTI index field 625 matches the TTI of a transmission of theuplink data 611, the UE 205 determines that the control signal 620corresponds to the uplink data 611. Otherwise, if the target TTI doesnot match the TTI of the initial uplink data transmission at 610 or asubsequent transmission repetition at 615, then the UE 205 determinesthe control signal 620 does not correspond to the uplink data 611 andinterprets the control signal 620 conventionally.

In the depicted embodiment, the control signal 620 corresponds to theinitial uplink data transmission (item 610) and the UE 205 examines theindicator 630 to determine whether the uplink data 611 was successfullyreceived by the gNB 210. In certain embodiments, the indicator 630replaces the NDI field in an UL grant. Typically, the NDI field containsone bit indicating whether the UL grant is for new data or is to be usedfor UL transmission repetition. However, when the indicator 630 replacesthe NDI field, the corresponding bit is interpreted as ACK/NAK bit. Inone embodiment, a bit value of “1” in the NDI field indicates the uplinkdata 611 was successfully received (“ACK”) while a bit value of “0” inthe NDI field indicates that the uplink data 611 was unsuccessfullyreceived (“NAK”). In the case of ACK, the UE 205 terminates transmissionrepetition of uplink data 611. However, in the case of NAK, the UE 205retransmits the uplink data 611. In one embodiment, the UE 205retransmits the uplink data 611 using grant-free transmissionrepetition. Here, the UE 205 continues transmission repetition 615 ofthe uplink data 611 until either receiving subsequent indication ofsuccessful reception or until the number of repetitions reaches K. Inother embodiments, the UE 205 retransmits the uplink data 611 usinggrant-based transmission 635, for example using UL resources scheduledin the control signal 620.

FIG. 7 depicts a procedure 700 for early termination of uplinktransmission repetition by using a predetermined TTI offset to indicatecorrespondence between a DL control signal and previously received ULdata (e.g., the UL TB 215). The procedure 700 involves communicationbetween the UE 205 and the gNB 210. The UE 205 may be one embodiment ofthe remote unit 105 and/or the remote apparatus 300, discussed above.The gNB 210 may be one embodiment of the base unit 110 and/or the basestation apparatus 400, discussed above.

As depicted, the procedure 700 begins and the UE 205 receives aconfiguration signal from the gNB 210 (see item 703). The configurationsignal includes the predetermined TTI offset value. At a later point intime, the UE 205 generates uplink data to be transmitted to the gNB 210(see item 705). Accordingly, the UE 205 sends an uplink datatransmission (item 710) to the gNB 210, the uplink data transmissionincluding uplink data 711. Here, the uplink data 711 may be oneembodiment of the UL TB 215 discussed above. In some embodiments, the UE205 sends the uplink data transmission using grant-free UL transmissionresources. For example, the gNB 210 may preconfigure a transmissionresource pool for grant-free UL transmission for URLLC service.

The UE 205 is configured to send K repetitions of the uplink data 711,where K is a predetermined value (e.g., previously configured by the gNB210). Here the K repetitions includes the initial uplink datatransmission (item 710) and one or more subsequent transmissionrepetitions (item 715). Each subsequent transmission repetition includesa copy of the uplink data 711. Here, the initial transmission is sent ona first TTI, while the one or more subsequent transmission repetitionsare send on subsequent TTIs.

After receiving the initial uplink data transmission (or a subsequenttransmission repetition), the gNB 210 determines whether the uplink data711 is successfully received. The uplink data 711 is successfullyreceived when the gNB 210 is able to decode it. Similarly, the uplinkdata 711 is not successfully received when the gNB 210 is unable todecode it. Next, the gNB 210 generates a control signal 720, such as aDCI and/or UL grant, for transmission to the UE 205. As depicted, thecontrol signal 720 includes an indicator 730. Here, the control signal720 does not require a TTI offset field because the TTI offset ispreconfigured by the gNB 210. The indicator 730 indicates whether theuplink data 711 is successfully received at the gNB 210.

To indicate that the control signal 720 corresponds to the initialuplink data transmission, the gNB 210 transmits the control signal 720during a specific TTI based on the preconfigured TTI offset. Forexample, if the initial uplink data transmission is sent during a firstTTI having a value of “Z” and the preconfigured TTI offset has a valueof “X”, then the gNB 210 transmits the control signal 720 during asecond TTI having a value of “Y”, such that “Y”−“X”=“Z”. To indicatethat the control signal 720 corresponds to a subsequent transmissionrepetition, the gNB 210 transmits the control signal 720 during aspecific TTI based on the preconfigured TTI offset and on the TTI of asubsequent transmission repetition.

The TTI offset between the UE 205 transmitting the grant-free PUSCH(e.g., the initial uplink data transmission at 710 or a subsequenttransmission repetition at 715) and the gNB 210 transmitting the controlsignal 720 is dependent on processing capabilities of the UE 205 and gNB210 as well as latency requirements of the URLLC service. Generally, theconfigured TTI offset is set as the smallest interval needed (e.g.,based on the processing capabilities the UE 205 and the gNB 210).Further, if the uplink data 711 is successfully decoded at the gNB, thenthe gNB 210 to send an acknowledgment (e.g., an ACK) to the UE 205 forthe UE 205 to stop transmission repetition of the uplink data 711 beforethe number of repetitions (e.g., number of total transmissions of theuplink data 711) reaches K.

Upon receiving control signal 720, the UE 205 identifies the TTI (e.g.,of value “Y”) of the control signal 720 and calculates a target TTI of“Y”−“X” using the preconfigured TTI offset of “X”. If the target TTImatches the first TTI (e.g., TTI of “Z”), then the UE 205 determinesthat the control signal 720 corresponds to the initial uplink datatransmission. If the target TTI matches the TTI of a subsequenttransmission repetition, the UE 205 determines that the control signal720 corresponds to subsequent transmission repetition. Otherwise, if thetarget TTI does not match the TTI of a transmission of the uplink data711, then the UE 205 determines the control signal 720 does notcorrespond to the uplink data 711 and interprets the control signal 720conventionally.

In the depicted embodiment, the control signal 720 corresponds to theinitial uplink data transmission (item 710) and the UE 205 examines theindicator 730 to determine whether the uplink data 711 was successfullyreceived by the gNB 210. In certain embodiments, the indicator 730replaces the NDI field in an UL grant. Typically, the NDI field containsone bit indicating whether the UL grant is for new data or is to be usedfor UL transmission repetition. However, when the indicator 730 replacesthe NDI field, the corresponding bit is interpreted as ACK/NAK bit. Inone embodiment, a bit value of “1” in the NDI field indicates the uplinkdata 711 was successfully received (“ACK”) while a bit value of “0” inthe NDI field indicates that the uplink data 711 was unsuccessfullyreceived (“NAK”). In the case of ACK, the UE 205 terminates transmissionrepetition of uplink data 711. However, in the case of NAK, the UE 205retransmits the uplink data 711. In one embodiment, the UE 205retransmits the uplink data 711 using grant-free transmissionrepetition. Here, the UE 205 continues transmission repetition 715 ofthe uplink data 711 until either receiving subsequent indication ofsuccessful reception or until the number of repetitions reaches K. Inother embodiments, the UE 205 retransmits the uplink data 711 usinggrant-based transmission 735, for example using UL resources scheduledin the control signal 720.

FIG. 8 depicts one embodiment of a method 800 for early termination ofuplink transmission repetition, according to embodiments of thedisclosure. In some embodiments, the method 800 is performed by a remoteunit, such as the remote unit 105, UE 205, and/or the remote apparatus300, described above. In certain embodiments, the method 800 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

The method 800 begins and transmits 805 data to a base unit in a firstTTI. In some embodiments, the data is a UL TB. In certain embodiments,the data (e.g., UL TB) is configured for transmission with apredetermined number of repetitions. For example, the uplink data may beinitially transmitted on a first TTI and configured to be retransmittedduring one or more additional TTIs. In one embodiment, the transmitting805 the data in the first TTI includes sending an initial transmissionof the data. In another embodiment, the transmitting 805 the data in thefirst TTI includes sending a retransmission of the data (e.g., asubsequent transmission repetition). The method 800 includes receiving810 a control signal from the base unit in a second TTI. Here, thesecond TTI is later than the first TTI. In certain embodiments, thecontrol signal is a DCI and/or a UL grant.

The method 800 includes determining 815 whether the control signalcorresponds to the data. In certain embodiments, determining 815 whetherthe control signal corresponds to the data includes identifying a TTIindex contained in the control signal and determining whether theidentified TTI index matches to the first TTI (or to the TTI of atransmission repetition of the data). Here, the control signalcorresponds to the data in response to the identified TTI index matchingthe first TTI (or the TTI of a transmission repetition).

In some embodiments, determining 815 whether the control signalcorresponds to the data includes identifying a TTI offset, calculating aTTI from the second TTI and the identified TTI offset, and determiningwhether the calculated TTI matches to the first TTI (or to the TTI of atransmission repetition of the data). Here, the control signalcorresponds to the data in response to the calculated TTI matching thefirst TTI (or the TTI of a transmission repetition). In certainembodiments, identifying the TTI offset comprises identifying the TTIoffset from a bit field contained in the control signal. In oneembodiment, the bit field contained in the control signal indicates aspecific TTI offset from a set of TTI offsets. Here, the set of TTIoffsets may be preconfigured by the base unit or predefined in thecommunication standard specification. In other embodiments, the TTIoffset is a fixed value. In another embodiment, the TTI offset ispreconfigured by the base unit prior to transmitting 805 the data.

The method 800 also includes determining 820 whether to cease at leastone transmission repetition of the data before the number of repetitionsreaches the predetermined number (e.g., whether cease any remainingtransmission repetitions), in response to the control signalcorresponding to the data. In some embodiments, the control signalcomprises an indicator for indicating whether the data is successfullyreceived.

In such embodiments, determining 820 whether to cease at least onetransmission repetition of the data before the number of repetitionsreaches the predetermined number includes determining, from theindicator, whether the data is successfully received and ceasing anyremaining transmission repetitions of the data number in response to theindicator indicating that the data is successfully received. In oneembodiment, determining 820 whether to cease at least one transmissionrepetitions of the data before the number of repetitions reaches thepredetermined number includes continuing transmission repetitions of thedata until the number of repetitions reaches the predetermined number inresponse to the indicator indicating that the data is not successfullyreceived. In another embodiment, determining 820 whether to cease atleast one transmission repetitions of the data before the number ofrepetitions reaches the predetermined number includes transmitting thedata based on scheduling of the control signal in response to theindicator indicating that the data is not successfully received.

The indicator may be an NDI in the control signal, wherein the NDI isreinterpreted to determine whether the data is successfully received.The method 800 ends.

FIG. 9 is a schematic flow chart diagram illustrating one embodiment ofa method 900 for early termination of uplink transmission repetition,according to embodiments of the disclosure. In some embodiments, themethod 900 is performed by a base unit, such as the base unit 110, thegNB 210, and or the base station apparatus 400. In certain embodiments,the method 900 may be performed by a processor executing program code,for example, a microcontroller, a microprocessor, a CPU, a GPU, anauxiliary processing unit, a FPGA, or the like.

The method 900 begins and receives 905 data from a remote unit in afirst transmission time interval (“TTI”), wherein the data is configuredfor transmission with a predetermined number of repetitions. Forexample, the uplink data may be initially transmitted in the first TTIand configured to be retransmitted during one or more additional TTIs.In one embodiment, receiving 905 the data includes receiving an uplinksignal containing the uplink data at a receiver. The method 900 includesdetermining 910 whether the data is successfully received. Here, thedata is determined to be “successfully received” when the data from theuplink signal is successfully decoded. In one embodiment, the datareceived in the first TTI is an initial transmission of the data. Inanother embodiment, the data received in the first TTI is aretransmission of the data (e.g., a subsequent transmission repetition).

The method 900 includes transmitting 915 a control signal to the remoteunit in a second TTI, the control signal corresponding to the data andincluding an indicator of whether the data is successfully received. Incertain embodiments, the control signal uses a TTI offset between thefirst TTI and the second TTI to indicate association between the controlsignal and the data. In one embodiment, the control signal includes abit field for indicating the TTI offset. For example, the bit fieldincluded in the control signal may indicate a specific TTI offset from aset of TTI offsets, the set of TTI offsets being preconfigured for theremote unit or predefined in the communication standard specification.In other embodiments, the TTI offset between the first TTI and thesecond TTI is a fixed value or is preconfigured for the remote unitbefore the remote unit transmits the data. In some embodiments, thecontrol signal includes a bit field for indicating a TTI index of thefirst TTI to designate association between the control signal and thedata.

In one embodiment, the indicator for indicating whether the data issuccessfully received is realized by repurposing a NDI field in thecontrol signal. Here, the value in the NDI field is used to indicatewhether the data is successfully received. In another embodiment, theNDI field is replaced by the indicator. In certain embodiments, theindicator in the control signal may be one bit (e.g., an ACK/NAK bit)whose value indicates whether the data is successfully received. Whenthe indicator indicates that the data is successfully received, then theremote unit ceases transmission repetition of the data (e.g., UL TB)before the number of repetitions reaches the predetermined number. Themethod 900 ends.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a transmitter thattransmits data to a base unit in a first transmission time interval(“TTI”), wherein the data is configured for transmission with apredetermined number of repetitions; a receiver that receives a controlsignal from the base unit in a second TTI prior to completingtransmission of the predetermined number of repetitions; and a processorthat: determines whether the control signal corresponds to the data, inresponse to determining that the control signal corresponds to the data,ceases transmission of at least one repetition of the data before thenumber of repetitions reaches the predetermined number of repetitions;and in response to determining that the control signal fails tocorrespond to the data, continues to transmit at least one additionalrepetition of the data.
 2. The apparatus of claim 1, wherein determiningwhether the control signal corresponds to the data comprises theprocessor: identifying a TTI offset, calculating a TTI from the secondTTI and the identified TTI offset, and determining whether thecalculated TTI matches to the first TTI, wherein the control signalcorresponds to the data in response to the calculated TTI matching thefirst TTI and the control signal fails to correspond to the data inresponse to the calculated TTI failing to match the first TTI.
 3. Theapparatus of claim 2, wherein the processor identifies the TTI offsetfrom a bit field contained in the control signal.
 4. The apparatus ofclaim 3, wherein the bit field contained in the control signal indicatesa TTI offset from a set of TTI offsets, the set of TTI offsets beingpreconfigured by the base unit.
 5. The apparatus of claim 2, wherein theTTI offset is a fixed value.
 6. The apparatus of claim 2, wherein theTTI offset is preconfigured by the base unit prior to the transmittertransmitting the data.
 7. The apparatus of claim 1, wherein determiningwhether the control signal corresponds to the data comprises theprocessor: identifying a TTI index contained in the control signal, anddetermining whether the identified TTI index matches to the first TTI,wherein the control signal corresponds to the data in response to theidentified TTI index matching the first TTI and the control signal failsto correspond to the data in response to the identified TTI indexfailing to match the first TTI.
 8. The apparatus of claim 1, wherein thecontrol signal comprises an indicator for indicating whether the data issuccessfully received, wherein determining whether to cease at least onetransmission repetition of the data before the number of repetitionsreaches the predetermined number comprises the processor determining,from the indicator, whether the data is successfully received, whereinthe transmitter: ceases at least one transmission repetition of the databefore the number of repetitions reaches the predetermined number inresponse to the indicator indicating that the data is successfullyreceived, and continues repeating the data until the number ofrepetitions reaches the predetermined number in response to theindicator indicating that the data is not successfully received.
 9. Theapparatus of claim 8, wherein determining, from the indicator, whetherthe data is successfully received comprises the processor reinterpretinga new data indicator (“NDI”) in the control signal, the reinterpretedNDI indicating whether the data is successfully received.
 10. Theapparatus of claim 1, wherein the control signal comprises an indicatorfor indicating whether the data is successfully received, whereinceasing at least one transmission repetition of the data before thenumber of repetitions reaches the predetermined number is based on theprocessor determining, from the indicator, whether the data issuccessfully received, wherein the transmitter: ceases at least onetransmission repetition of the data before the number of repetitionsreaches the predetermined number in response to the indicator indicatingthat the data is successfully received, and transmits the data based onscheduling of the control signal in response to the indicator indicatingthat the data is not successfully received.
 11. The apparatus of claim10, wherein determining, from the indicator, whether the data issuccessfully received comprises the processor reinterpreting a new dataindicator (“NDI”) in the control signal, the reinterpreted NDI being theindicator.
 12. An apparatus comprising: a receiver that receives datafrom a remote unit in a first transmission time interval (“TTI”),wherein the data is configured for transmission with a predeterminednumber of repetitions; a processor that determines whether the data issuccessfully received; and a transmitter that transmits a controlsignal, corresponding to the data, to the remote unit in a second TTIprior to the remote unit completing transmission of the data with thepredetermined number of repetitions, wherein the control signalcomprises an indicator for indicating whether the data is successfullyreceived and receipt of one or more repetitions of the data is ceasedsubsequent to transmission of the control signal corresponding to thedata.
 13. The apparatus of claim 12, wherein the control signal uses aTTI offset between the first TTI and the second TTI to indicateassociation between the control signal and the data.
 14. The apparatusof claim 13, wherein the control signal includes a bit field forindicating the TTI offset.
 15. The apparatus of claim 14, wherein thebit field included in the control signal indicates a TTI offset from aset of TTI offsets, the set being preconfigured for the remote unit. 16.The apparatus of claim 13, wherein the TTI offset between the first TTIand the second TTI is a fixed value.
 17. The apparatus of claim 13,wherein the TTI offset is preconfigured for the remote unit before theremote unit transmits the data.
 18. The apparatus of claim 12, whereinthe control signal includes a bit field for indicating a TTI index ofthe first TTI to designate association between the control signal andthe data.
 19. The apparatus of claim 12, wherein the indicator forindicating whether the data is successfully received replaces a new dataindicator (“NDI”) in the control signal.
 20. The apparatus of claim 12,wherein the indicator for indicating whether the data is successfullyreceived is realized by one bit in the control signal.